fix: add polyfills / avoid using structuredClone
#915
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
I don't want to touch core-js with a bargepole. This is the effect of those two imports on the bundle size:
Let's find another approach, whether that's writing our own polyfill or avoiding those features |
- polyfills for `at` and `withResolvers` - avoid using `structuredClone`, we can use `JSON.parse(JSON.stringify(..))` instead at that position makes the site work in more browsers closes #911
|
wow, that's bad - I created our own polyfills instead |
|
Can you let me know when this is deployed to the site, so that I can test it for you? |
|
It's deployed already |
|
It's definitely still broken. Safari 14:
Safari 15 / 16 / 17:
|
|
Well that's odd. I only have 17.6 installed here but it works fine. Both places that use |
|
I did a hard refresh, so I don't know? CloudFlare maybe? |
|
The Polyfill for Array.prototype.at does not handle |
atandwithResolversstructuredClone, we can useJSON.parse(JSON.stringify(..))instead at that positionmakes the site work in more browsers
closes #911 assuming we're fine with not supporting Safari 13 and lower (or similarly old browsers; i.e. earlier than ~2020)